The storage command node includes the following subnode commands:
hastatus
pools
units
Note: The device IDs for storage pools and storage units must be unique within a cluster.
Each of the subnode commands, and the leaf node commands attached to them, are described in detail, with parameters and arguments listed for each command.
Examples of command usage are included in the discussions.
CLI:
storage hastatus show [-deviceid device_ID]
GUI: Navigate to the Storage Pools → Pool HA Status node. To display information about a specific storage pool, select it from the table and run the Show command from the drop-down menu of the action pane.
The storage hastatus show command displays the high-availability status of a specified storage pool or of all storage pools. Run the command with the -name parameter to display information about a specific storage pool, or without any parameter to display information about all storage pools. The following information is displayed:
Pool name
Primary server
Active (secondary) servers
Passive (secondary) servers
[-deviceid device_ID]
This specifies the device ID of a storage pool for which HA status is to be displayed.
The following example displays HA status for all storage pools in the cluster:
spinserver::> storage hastatus show
Pool Primary Server Active Servers Passive Servers
pool0 ServerA ServerB ServerC
pool1 ServerA ServerC ServerB
pool2 ServerC ServerB ServerA
The following example displays HA status information for the storage pool named pool2:
spinserver::> storage hastatus show -deviceid pool2 Pool pool2 Primary Server ServerC Active Servers ServerB Passive Servers ServerA
The storage pools command subnode includes the following leaf-node commands:
addpassivesecondary
delete
demoteactivesecondary
disconnect
failover
forcediscovery
grow
modify
new
promotepassivesecondary
removesecondary
revertpools
setoffline
setonline
setpriority
show
show-home
show-local
sync
CLI:
storage pools addpassivesecondary -deviceid device_ID -passivesec spinserver -priority priority
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Add Passive Secondary command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Add Passive Secondary.
The storage pools addpassivesecondary command adds a passive secondary server to a storage pool in a high-availability (HA) configuration.
Note: If the number of active secondary servers for the storage pool is set to greater than zero, the first passive secondary server that was created is automatically promoted to active secondary.
Note: An individual SpinServer can serve as secondary to no more than four storage pools, whether as active secondary or passive secondary.
-deviceid device_ID
This specifies the device ID of the storage pool to which the passive secondary server is to be added.
-passivesec spinserver
This specifies the SpinServer that is to be added as a passive secondary server.
-priority priority
This specifies the takeover priority of the passive secondary server. Possible values range from 1 (lowest priority) to 64 (highest priority). For instance, if an HA configuration includes a server named ServerA that has a priority of 2 and a server named ServerB that has a priority of 1, ServerA is promoted as an active secondary before ServerB if the primary or active secondary fails.
The following example adds a SpinServer named newServer as a passive secondary server to a storage pool named sp0. The takeover priority of the new server is set to 2.
spinserver::> storage pools addpassivesecondary -deviceid sp0 -passivesec newServer -priority 2
CLI:
storage pools delete -deviceid device_ID
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Delete command from the drop-down menu of the action pane.
The storage pools delete command destroys the contents of the storage pool, freeing all the resources that the pool occupied. This is primarily useful for reusing the storage pool's storage units to create a new storage pool. To create a new storage pool after deleting the old one, use the storage pools new command.
Note: Only storage pools in the offline state can be deleted. Before deleting a storage pool, run the storage pools setoffline command.
-deviceid device_ID
This is the device ID of the storage pool. If you do not provide a value for the -deviceid parameter, a device name of the form poolnumber is automatically generated, where number is a sequential integer (for instance, 0, 1, 2, and so on). This is to ensure that new storage pools are given unique device IDs across the cluster.
The following command example deletes a storage pool named sp0.
spinserver::> storage pools delete -deviceid sp0
CLI:
storage pools demoteactivesecondary -deviceid device_ID -secondary spinserver
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Demote Active Secondary command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Demote Active Secondary.
The storage pools demoteactivesecondary command demotes an active secondary server to passive secondary status in an HA configuration.
Note: An individual SpinServer can serve as secondary to no more than four storage pools, whether as active secondary or passive secondary.
-deviceid device_ID
This specifies the device ID of the storage pool.
-secondary spinserver
This specifies the SpinServer that is to be demoted to passive secondary status.
The following example demotes a SpinServer named Server2 to passive secondary status.
spinserver::> storage pools demoteactivesecondary -secondary Server2
CLI:
storage pools disconnect -deviceid device_ID
GUI: Navigate to the Storage Pools → Storage Pools node, then select a storage pool from the table and run the Disconnect command from the drop-down menu of the action pane.
Before using the storage pools disconnect command, run the storage pools setoffline command. The storage pools disconnect command temporarily disconnects a storage pool from the cluster. This is useful if the physical disks that comprise the storage pool are moved to another disk enclosure. If this is done, the storage pools forcediscovery command must be run on the server to rediscover the storage pool. If the primary SpinServer is restarted, the storage pool is again registered with the cluster. Do not use this command if you need to reuse a storage pool's storage units to create a new storage pool. For that purpose, use the storage pools delete command.
The following command example temporarily disconnects a storage pool named sp0.
spinserver::> storage pools disconnect -deviceid sp0
CLI:
storage pools failover -deviceid device_ID -activesec active_secondary
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Failover command from the drop-down menu of the action pane. Enter the appropriate values in the table that is displayed, then click Failover.
The storage pools failover command forces a storage pool to fail over to one of its active secondary SpinServers.
-deviceid device_ID
This is the device ID of the storage pool.
-activesec active_secondary
This is the name of the active secondary that is to take over as the primary for the storage pool.
The following example forces a storage pool named sp0 to fail over to the active secondary named backupServer.
spinserver::> storage pools failover -deviceid sp0 -activesec backupServer
CLI:
storage pools forcediscovery
GUI: Navigate to the Storage Pools → Storage Pools node, then run the Force Discovery command from the top bar of the action pane.
In the event of an error in the RAID subsystem, or if the physical disks that comprise a storage pool have been moved to another enclosure, storage pools need to be rediscovered to bring the pools back online. To force the discovery of all storage pools, use the storage pools forcediscovery command. After running the command, the storage pools enter the busy state while a quick verification process is performed. After verification is complete, the pools are online and ready for normal VFS operations.
The following command example forces the discovery of all storage pools.
spinserver::> storage pools forcediscovery
CLI:
storage pools grow -deviceid device_ID -sunits [storage_units]
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Grow command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Grow.
The storage pools grow command increases the storage capacity of a storage pool by adding additional storage units (RAID sets or expansion JBOD disks) to the storage pool.
-deviceid device_ID
This is the device ID of the storage pool.
-sunits [storage_units]
This is the square-bracketed, comma-separated list of storage units (RAID sets or expansion JBOD disks) to be added to the storage pool.
The following command example adds storage units su0, su1, and su2 to a storage pool named sp0.
spinserver::> storage pools grow -deviceid sp0 -sunits [su0,su1,su2]
CLI:
storage pools modify -deviceid device_ID [-freespacealarm free_space_alarm_threshold] [-homeserver home_spinserver]
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Show command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then run the Modify command.
The storage pools modify command sets the free-space alarm threshold and the home SpinServer of a storage pool.
The free-space alarm is triggered when a specified threshold of remaining space is reached. The alarm is issued in the form of a critical event that can be relayed to administrators via a subscription, an SNMP trap destination, or both. See the Administration Guide for information on setting up critical-event subscriptions and SNMP trap destinations.
In a high-availability (HA) configuration, storage pools can fail over from one SpinServer to another. After a failover, you can use the storage pools revertpools command to return storage pools to their home SpinServers. By default, a storage pool's home SpinServer is the SpinServer on which the storage pool was created; however, you can use the storage pools modify command to change a storage pool's home SpinServer.
-deviceid device_ID
This is the device ID of the storage pool.
[-freespacealarm free_space_alarm_threshold]
This specifies the percentage of free space remaining on the storage pool before the free-space alarm is triggered. For instance, setting a value of 5 triggers an alert when 5% of free space remains on the storage pool; that is, when the storage pool is 95% full. Possible values are integers from 1 to 50, or 0 to disable the free-space alarm. The default is 5.
[-homeserver home_spinserver]
This specifies the storage pool's home SpinServer.
The following command example sets the free-space alarm threshold to 10 percent on a storage pool named sp0.
spinserver::> storage pools modify -deviceid sp0 -freespacealarm 10
CLI:
storage pools new -deviceid device_ID -layout layout -freespacealarm free_space_alarm_threshold -sunits [storage_units]
GUI: Navigate to the Storage Pools → Storage Pools node, then click New in the top bar of the action pane. Enter the appropriate values into the table that is displayed, then click Create.
The storage pools new command creates a new storage pool. Storage pools are constructed from one or more storage units (RAID sets or expansion JBOD disks), providing a much larger block address space than is possible with only one RAID set or expansion JBOD. The primary purpose of a storage pool is to serve as a container for virtual file systems (VFSs). The SpinServer on which the storage pools new command is run becomes the primary server for the new storage pool. In a high-availability (HA) configuration, each storage pool is served by one primary server and one or more secondary servers. The primary server controls reads and writes to the storage pool; however, if the primary server fails, one of the secondary servers assumes control of the storage pool.
-deviceid device_ID
This is the device ID of the created storage pool. If you do not provide a value for this parameter, a device name of the form poolnumber is automatically generated, where number is a sequential integer (for instance, 0, 1, 2, and so on). This is to ensure that new storage pools are given unique device IDs across the cluster.
-layout layout
Layout describes the configuration of the data on the storage units. Possible values include concatenation and stripe. The default is stripe.
-freespacealarm free_space_alarm_threshold
This specifies the percentage of free space remaining on the storage pool before the free-space alarm is triggered. For instance, setting a value of 5 triggers an alert when 5% of free space remains on the storage pool; that is, when the storage pool is 95% full. Possible values are integers from 1 to 50, or 0 to disable the free-space alarm. The default is 5.
-sunits [storage_units]
This is the square-bracketed, comma-separated list of storage units (RAID sets or expansion JBOD disks) assigned to the storage pool. If a value is not specified for the parameter, all unused storage units are used by default. If you are using the CLI and press the Tab key after typing the -sunits parameter, all unused storage units are automatically listed.
The following command example creates a storage pool named sp1 that uses storage units named su0, su1, and su2. The layout is designated as stripe. The free-space alarm threshold is set to 5 percent. The storage pool's primary server is the SpinServer on which the command is issued.
spinserver::> storage pools new -deviceid sp1 -layout stripe -sunits [su0,su1,su2] -freespacealarm 5
CLI:
storage pools promotepassivesecondary -deviceid device_ID -passivesec spinserver
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Promote Passive Secondary command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Promote Passive Secondary.
The storage pools promotepassivesecondary command promotes a passive secondary server to active secondary status in an HA configuration.
Note: If the number of active secondary servers for the storage pool is set to greater than zero, the first passive secondary server that was created is automatically promoted to active secondary.
Note: An individual SpinServer can serve as secondary to no more than four storage pools, whether as active secondary or passive secondary.
-deviceid device_ID
This specifies the device ID of the storage pool.
-passivesec spinserver
This specifies the SpinServer that is to be promoted to active secondary status.
The following example promotes a SpinServer named newServer to active secondary status for storage pool sp0.
spinserver::> storage pools promotepassivesecondary -deviceid sp0 -passivesec newServer
CLI:
storage pools removesecondary -deviceid device_ID -secondary spinserver
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Remove Secondary command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Remove Secondary.
The storage pools removesecondary command removes a secondary server from a storage pool in a high-availability (HA) configuration.
-deviceid device_ID
This specifies the device ID of the storage pool.
-secondary spinserver
This specifies the SpinServer that is to be removed as a secondary.
The following example removes a secondary server named Server3 from the storage pool named sp0 in a high-availability configuration:
spinserver::> storage pools removesecondary -deviceid sp0 -secondary Server3
CLI:
storage pools revertpools -deviceids [list_of_pools]
GUI: Navigate to the Storage Pools → Storage Pools node, then click the Revert Pools command in the top bar of the action pane. Enter the appropriate information into the table that is displayed, then click Revert Pools.
The storage pools revertpools command reverts one or more storage pools to their home SpinServers; that is, returns one or more storage pools that have failed over to other SpinServers back to their home SpinServers. This is useful after storage-pool failover. By default, the command reverts all storage pools to their home SpinServers.
-deviceids [list_of_pools]
This is the list of storage pools that are to be reverted. If you are using the CLI, press Tab after typing the parameter to get a complete list of storage pools.
The following example reverts storage pools pool0 and pool1 to their home SpinServers:
spinserver::> storage pools revertpools -deviceids [pool0,pool1]
CLI:
storage pools setoffline -deviceid device_ID
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Take Offline command from the drop-down menu of the action pane.
The storage pools setoffline command takes a storage pool offline. Using this command prohibits further access to the storage pool and takes all of the pool's VFSs offline. The storage pool remains offline across system restarts.
Note: Before using the storage pools disconnect command, run the storage pools setoffline command.
Note: Only storage pools in the offline state can be deleted. Before deleting a storage pool, run the storage pools setoffline command.
The following command example takes offline a storage pool named sp0.
spinserver::> storage pools setoffline -deviceid sp0
CLI:
storage pools setonline -deviceid device_ID -newprimary primary_server
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Bring Online command from the drop-down menu of the action pane. Enter the appropriate information into the table that is displayed, then clickBring Online.
The storage pools setonline command brings a storage pool back online after the storage pools setoffline or storage pools disconnect command is run.
-deviceid device_ID
This is the device ID of the storage pool.
-newprimary primary_server
This is the primary SpinServer of the storage pool that is being set online. The default value is the storage pool's home SpinServer.
The following example brings online a storage pool named sp0 on a primary SpinServer named Server1:
spinserver::> storage pools setonline -deviceid sp0 -newprimary Server1
CLI:
storage pools setpriority -passivesec spinserver -priority priority
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Set Priority command from the drop-down menu of the action pane. Enter the appropriate values into the table that is displayed, then click Set Priority.
The storage pools setpriority command sets the takeover priority for a passive secondary server in a high-availability (HA) configuration. Priority 1 (one) is highest.
-passivesec spinserver
This specifies the SpinServer that is to have its takeover priority set.
-priority priority
This specifies the takeover priority for the passive secondary. Possible values range from 1 (lowest priority) to 64 (highest priority). For instance, if an HA configuration includes a server named ServerA that has a priority of 2 and a server named ServerB that has a priority of 1, ServerA is promoted as an active secondary before ServerB if the primary or active secondary fails.
The following example sets the takeover priority to 1 for a passive secondary server named Server3:
spinserver::> storage pools setpriority -passivesec Server3 -priority 1
CLI:
storage pools show [-deviceid device_ID]
GUI: Navigate to the Storage Pools → Storage Pools node. To display information about a specific storage pool, select it from the table and run the Show command from the drop-down menu of the action pane.
The storage pools show command displays information about a storage pool if the -deviceid parameter is specified and information about all storage pools if the parameter is not specified. After identification of the storage pool or pools has been made, the following information is displayed. A subset of this information is displayed if the -deviceid parameter is not specified.
Device ID (storage pool name)
UUID
Status (online, offline, busy, active, or passive)
Layout
Group size (in MB blocks)
Total storage pool size (in MB blocks)
MB blocks used
MB blocks available
Percentage of MB blocks used
Free-space alarm threshold (percentage)
Number of VFSs on the storage pool or pools
List of storage units that are known to the SpinServer
List of storage units that are required for the storage pool
Maximum number of active servers
Home server name
Primary server name
List of active secondary servers
List of passive secondary servers
Pool version
NVRAM version
Server priorities for failover
[-deviceid device_ID]
This is the device ID of the storage pool for which to display specific information.
The following command example displays information about all storage pools.
spinserver::> storage pools show
Device ID Status Size (MB) Available Use% # VFS Primary Server
(MB)
sp0 online 833316 54571 93.5% 470 Server2
sp1 online 416543 360721 13.4% 5 Server2
The following example displays information about a storage pool named sp0.
spinserver::> storage pools show -deviceid sp0 Device ID sp0 UUID 66b1714033b80b00336b6d696e370000 Status online Layout stripe Group Size (MB) 512 Size (MB) 138848 Used 20336 Avail 118512 Use% 14.6% Free Space Alarm Threshold (%) 1 # VFS 172 Storage Units Present su0 Storage Units Required su0 Max # Actives 1 Home Server Server1 Primary Server Server1 Active Servers Server2 Passive Servers Pool Version 17321 NVRAM Version 17321 Server Priorities Server2:1, Server1:64
CLI:
storage pools show-home [-deviceid device_ID]
GUI: Navigate to the Storage Pools → Storage Pools node. To display information about a specific storage pool, select it from the table and run the Show command from the drop-down menu of the action pane.
The storage pools show-home command displays the home SpinServers for one or more storage pools.
[-deviceid device_ID]
This is the device ID of the storage pool for which to display specific information.
The following command example displays the home SpinServer of all storage pools.
spinserver::> storage pools show-home
Device Home Server Primary Server
ID
pool0 Server1 Server1
pool1 Server1 Server2
pool2 Server1 Server1
pool3 Server1 Server2
CLI:
storage pools show-local [-deviceid device_ID]
GUI: Navigate to the Storage Pools → Storage Pools node. To display information about a specific storage pool, select it from the table and run the Show Local View command from the drop-down menu of the action pane.
The storage pools show-local command displays the following information about a storage pool. The information displayed is from the perspective of the SpinServer on which the command is issued, which is not necessarily the SpinServer that is the storage pool's primary server.
Device ID (storage pool name)
UUID
Status (online, offline, busy, active, or passive)
[-deviceid device_ID]
This is the device ID of the storage pool for which to display specific information.
The following command example displays information about all storage pools from the perspective of the SpinServer on which the command is issued.
spinserver::> storage pools show-local
Device UUID Status
ID
pool0 d28336404c2809007370696e5f62007f online
pool1 ed833640b1ae09007370696e5f62007f online
CLI:
storage pools sync -deviceid device_ID
GUI: Navigate to the Storage Pools → Storage Pools node, then select the appropriate storage pool from the table and run the Sync command from the drop-down menu of the action pane.
To prevent the loss of data when shutting down the system, you must synchronize from the cache to the disk all the input and output (I/O) activities that are pending on a single storage pool. To accomplish this synchronization, use the storage pools sync command.
The following command example synchronizes all input and output (I/O) activities that are pending on a storage pool named sp0.
spinserver::> storage pools sync -deviceid sp0
The storage units command node provides a view of the external RAID sets or JBOD disks as seen from the Fibre Channel Host Bus Adapters (HBAs). A single storage unit represents a single external RAID set or JBOD disk that has been used to create it. Storage units are used in the creation of storage pools. A storage pool can comprise 1 to 128 storage units. The following ranges or limitations are defined:
Up to 1024 storage units (RAID sets or JBOD disks) per SpinServer.
Up to 127 storage units (RAID sets or JBOD disks) per Fibre Channel loop.
Up to 32 logical unit numbers (LUNs) per RAID array.
The storage units subnode includes the following leaf-node commands:
clearerror
modify
show
CLI:
storage pools clearerror -deviceid device_ID
GUI: Navigate to the Storage Pools → Storage Units node, then select the appropriate storage pool from the table and run the Clear Error command from the drop-down menu of the action pane.
The storage units clearerror command clears an error status from a storage unit. A storage unit can be marked with an error in the event of a power failure or other system problem. You can determine whether a storage unit is marked with an error by using the storage units show command; error status is listed in the Error column of the command's output.
The following command example clears the error status from a storage unit named su0:
spinserver::> storage units clearerror -deviceid su0
CLI:
storage pools modify -deviceid device_ID -primaryhostchannel primary_host_channel -desiredphc {Auto | 0 | 1 | 2 | 3}
GUI: Navigate to the Storage Pools → Storage Units node, then select the appropriate storage pool from the table and run the Show command from the drop-down menu of the action pane. Make the appropriate changes to the table that is displayed, then run the Modify command from the drop-down menu.
The storage units modify command sets the primary host channel and the desired primary host channel for a storage unit.
-deviceid device_ID
This is the device ID of the storage unit.
-primaryhostchannel primary_host_channel
This is the primary host channel of the storage unit. Possible values are 0 and 1.
-desiredphc {Auto | 0 | 1 | 2 | 3}
This specifies the desired primary host channel for the Fibre Channel connection between the SpinServer and the storage unit. Acceptable values for the parameter include Auto, 0, 1, 2, and 3. If the value is specified as Auto, the SpinServer uses the primary channel that is selected by the Fibre Channel device; if the value is specified as 0, 1, 2, or 3, the SpinServer uses that value as the primary channel. The default value for a new storage unit is Auto.
The following command example sets the storage unit named su0 to use primary host channel 1, and sets the desired primary host channel to Auto:
spinserver::> storage units modify -deviceid su0 -primaryhostchannel 1 -desiredphc Auto
CLI:
storage units show [-deviceid device_ID]
GUI: Navigate to the Storage Pools → Storage Units node. To display information about a specific storage unit, select it from the table and run the Show command from the drop-down menu of the action pane.
The storage units show command displays information about all storage units if no parameter is specified or information about one storage unit if the parameter is specified. After identification of the storage unit or units has been made, the following information is displayed by the system. A subset of this information is displayed if the -deviceid parameter is not specified.
Device ID
World Wide name
LUN
Fibre Channel device (FCD) ID
D-Function (SpinFS) device ID
Primary host channel status
Primary host channel
Primary loop ID
Secondary host channel status
Secondary host channel
Secondary loop ID
RAID set ID
Type of RAID
Vendor
Product number
Revision number
Status (online, offline, or unknown)
Damaged status (true or false)
Error status (true or false)
Last error code
Description of last error
Storage space size (in GB) on the storage unit
[-deviceid device_ID]
This is the device identification of the storage unit is the integer device ID as seen by the Fibre Channel driver.
The following example displays information about all storage units.
spinserver::> storage units show
Device World Wide Name LUN RAID FCD Status Damaged? Error? Size
ID Set ID (GB)
su0 20000080e512555e 0 r0s0 0 Online false false 136
The following command example displays information about a storage unit named su0.
spinserver::> storage units show -deviceid su0 Device ID su0 World Wide Name 20000080e511632b LUN 0 FCD ID 0 D-Function Device ID 7 Primary Host Channel Status connected Primary Host Channel 1 Primary Loop ID 133 Secondary Host Channel Status connected Secondary Host Channel 0 Secondary Loop ID 132 RAID Set r1s0 Type RAID 5 Vendor SPINNET Product 1316-06v2 Revision 5785 Status Online Damaged? false Error? false Last Error Code 0 Error Description success Size (GB) 136
Copyright © 2004 Network Appliance, Inc.; copyright © 2003, 2004 Spinnaker Networks, LLC. All rights reserved. Specifications subject to change without notice.